repeatable read造句
例句与造句
- Prevents non - repeatable reads but phantom rows are still possible
防止不可重复的读取，但是仍可以有幻像行。 - This leaves you a choice between read committed and repeatable read
剩下的也就是在“授权读取”和“可重复读取”之间选择了。 - Repeatable read - rr
可重复读rr - Non repeatable read
不可重复读 - By default , mysql uses the repeatable read isolation level for all transactions
默认情况下， mysql对所有事务使用repeatable read隔离级别。 - It's difficult to find repeatable read in a sentence. 用repeatable read造句挺难的
- Incorrect concurrency can lead to problems such as dirty reads , phantom reads , and non - repeatable reads
不正确的并发可能导致脏读、幻读和不可重复读等问题。 - This is an important issue , but using repeatable read isn ' t the only way to resolve it
这是一个非常重要的问题，但是使用可重复读取并不是解决问题的唯一途径。 - For example , reading from a read - only look up table doesn t require repeatable read , and uncommitted read is sufficient
比如，读取只读的查找表不需要可重复读级别，未提交读级别就足够了。 - Readpast can only be specified in transactions operating at the read committed or repeatable read isolation levels
仅可在运行于read committed或repeatable read隔离级别的事务中指定readpast 。 - Specifies that a scan is performed with the same locking semantics as a transaction running at repeatable read isolation level
指定事务在repeatable read隔离级别运行时，使用相同的锁定语义执行一次扫描。 - If the transaction isolation mode is repeatable read , then the optimizer would base its choice purely on the estimated costs
如果事务隔离模式是可重复读（ repeatable read ） ，那么优化器会将其选择完全基于估算成本。 - For the four levels of isolation supported , table 6 shows whether phantom , dirty , or non - repeatable read is possible from strongest to weakest
针对受支持的四种隔离级别，表6列出了出现幻像读、脏读或不可重复读的可能性（从高到低） 。 - If the value is set to 1 , then the optimizer behaves as it does for value 0 if the transaction isolation mode is not repeatable read
如果将其值设置为1 ，那么当事务隔离模式不是可重复读（ repeatable read ）时，优化器的行为就与值为0时一样。 - For example , if a repeatable read transaction has a shared lock on a row , and the transaction then modifies the row , the shared row lock is converted to an exclusive row lock
例如，如果repeatable read事务具有用于某行的共享锁，并且该事务随后修改了该行，则共享行锁便会转换为排他行锁。 - Shared locks are held while the data is being read to avoid dirty reads , but the data can be changed before the end of the transaction , resulting in non - repeatable reads or phantom data
在正在读取数据时保持共享锁，以避免脏读，但是在事务结束之前可以更改数据，从而导致不可重复的读取或幻像数据。
更多例句： 下一页